Techniques for workload spawning

ABSTRACT

Techniques for spawning workloads are provided. A single repository is read once to obtain an image for a workload or files and resources for the image. The read operation spawns multiple, and in some cases, concurrent write operations, to instantiate the workload over a network as multiple occurrences or instances of the workload in multiple processing environments.

This application is a continuation of U.S. patent application Ser. No. 13/162,672, filed Jun. 17, 2011, which is incorporated herein by reference in its entirety.

BACKGROUND

Cloud computing is rapidly changing the Internet into a collection of clouds, which provide a variety of computing resources, storage resources, and, in the future, a variety of resources that are currently unimagined.

This new level of virtualization should have unbounded the physical and geographical limitations of traditional computing, but this is not yet the case largely in part because of current deficiencies managing and instantiating virtualized resources over a network. That is, enterprises have been reluctant to outsource resources to cloud environments because the level-of-effort required for migration remains fairly expensive.

For example, the difficulty associated with managing resources by creating and deleting a lot of resources at one time adds a problem that has not been addressed in the industry. For example, consider a situation where an administrator knows that a resource running Apache™ Hadoop™ XEN (Virtual Machine (VM) Monitor (VMM)) and other scalable services are not performing as they should be, and the administrator needs to provision another 50 resources to handle the increased capacity. The likely only technique in place for the administrator within the enterprise is one that manually clones each one of the needed resources individually and cannot take advantage of the native hardware features available in the underlying architecture, which may assist in making the work more efficient.

In fact, current cloning techniques cause a bottleneck at an enterprise's resource deployment facility. This same bottleneck problem occurs when an administrator needs to de-provision resources that are running. The issue also arises across many other problems sets associated with distributing and creating processes intelligently across a network.

So, if an enterprise needs to get a large number of resources into an enterprise system as quickly as possible, the traditional cloning technology uses a one-to-one cloning approach, which is very slow, largely manual, and inefficient.

Furthermore as resources are moved to cloud environments, new processes are often and regularly started and stopped as needed. In many situations, the number of processes that are started and stopped can be in the range of 10s, 100s, or even 1000s at a time. Current architecture arrangements and methodologies do not efficiently allow this to happen without also having to incur large overhead expenses during the process.

SUMMARY

Various embodiments of the invention provide techniques for workload spawning. Specifically, a method for workload spawning is presented.

A workload is configured with a deployment policy, an identity-based authentication mechanism, and an access-control mechanism. A first instance of the workload is deployed in a first processing environment utilizing the deployment policy, the identity-based authentication mechanism, and the access-control mechanism. The deployment policy is updated to reflect an occurrence of the first instance and the deployment of additional instances of the workload occurs to additional processing environments using and updating the deployment policy for each additional occurrence of the workload and enforcing the identity-based authentication mechanism and the access-control mechanism.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example architecture for workload spawning, according to the techniques presented herein.

FIG. 2 is a diagram of a method for workload spawning, according to an example embodiment.

FIG. 3 is a diagram of another method for workload spawning, according to an example embodiment.

FIG. 4 is a diagram of a workload spawning system, according to the techniques presented herein.

DETAILED DESCRIPTION

A “resource” includes a user, service, system, device, directory, data store, groups of users, combinations and/or collections of these things, etc. A “principal” is a specific type of resource, such as an automated service or user that acquires an identity. A designation as to what is a resource and what is a principal can change depending upon the context of any given network transaction. Thus, if one resource attempts to access another resource, the actor of the transaction may be viewed as a principal.

An “identity” is something that is formulated from one or more identifiers and secrets that provide a statement of roles and/or permissions that the identity has in relation to resources. An “identifier” is information, which may be private and permits an identity to be formed, and some portions of an identifier may be public information, such as a user identifier, name, etc. Some examples of identifiers include social security number (SSN), user identifier and password pair, account number, retina scan, fingerprint, face scan, etc.

A “workload” as used herein refers to a special type of resource, such as a Virtual Machine (VM), an Operating System (OS), a hardware device, an agent, and/or an application.

A “processing environment” defines a set of cooperating computing resources, such as machines (processor and memory-enabled devices), storage, software libraries, software systems, etc. that form a logical computing infrastructure. A “logical computing infrastructure” means that computing resources can be geographically distributed across a network, such as the Internet. So, one computing resource at network site X and be logically combined with another computing resource at network site Y to form a logical processing environment.

The phrases “processing environment,” “cloud processing environment,” and the term “cloud” may be used interchangeably and synonymously herein.

Moreover, it is noted that a “cloud” refers to a logical and/or physical processing environment as discussed above.

Various embodiments of this invention can be implemented in existing network architectures. For example, in some embodiments, the techniques presented herein are implemented in whole or in part in the Novell® operating system products, directory-based products, cloud-computing-based products, and other products distributed by Novell®, Inc., of Waltham, Mass.

Also, the techniques presented herein are implemented in machines, such as processor or processor-enabled devices. These machines are configured to specifically perform the processing of the methods and systems presented herein. Moreover, the methods and systems are implemented and reside within a non-transitory computer-readable storage media or machine-readable storage medium and are processed on the machines configured to perform the methods.

Of course, the embodiments of the invention can be implemented in a variety of architectural platforms, devices, operating and server systems, and/or applications. Any particular architectural layout or implementation presented herein is provided for purposes of illustration and comprehension only and is not intended to limit aspects of the invention.

It is within this context that embodiments of the invention are now discussed within the context of the FIGS. 1-4.

FIG. 1 is a diagram of an example architecture for workload spawning, according to the techniques presented herein. It is noted that the FIG. 1 is presented for purposes of illustration and comprehension. It is to be understood that other architectural arrangements can be used to achieve the teachings presented herein and below.

The components of the FIG. 1 are implemented in non-transitory and processor-readable storage medium and are executed on physical processors on one or more networks. Each processor specifically configured to execute the components.

The FIG. 1 is presented with reference to a variety of specific example situations that an enterprise utilizing cloud environments can encounter. These are presented for purposes of illustration only as other situations can occur as well and still benefit from the techniques presented herein and below.

At A (in the FIG. 1), the user (can be any type of principal (automated application, etc.)) originates a request against the system to create 13 (as one example) new workload/images to help handle the traffic in a web server cluster. The request starts in the processor and creates a single workload that can validate identity and provide policy to manage techniques presented herein.

At B, where the first workload is generated the content is bootstrapped. (Covered in more detail below with the processing discussed at B-1.) The workload is created; internal to the workload is an embedded process that includes identity validation that can create workloads. Also, it includes the policy to tell how to create workloads and instantiate those workloads. In the present example, a most effective algorithm with recursion is used to let the system interact and optimize how the images are created. There is also a way for using a single workload to instantiate all the other workloads as an alternative. One essential point is that there is spawning from the workloads themselves for purposes of fulfilling a request based upon dynamically evaluated policy parameters.

At B-1, this is the location of the files (repository) that are used in the workload. The technique is that the files are used via a single read operation from the location with multiple writes to the different locations to create multiple workload instances. This approach can be used with multiple existing or emerging technologies or used with a multicast that is pushed down to the machines and initiated. There are a few options when the workload data is deployed using an image, files, or combination of both to deploy. The workload can be an image that mimics a Pre-boot eXecution Environment (PXE) boot and loads a virtual image, processes on the virtualization platform to load the workload, or lays down the files for the image. There are many options that can be used, but the embodiments herein discuss how to distribute a workload between environments and machines and then instantiate the workload instances. As described, there are many hardware technologies that can be leveraged with the embodiments presented herein, which aren't being utilized today. For instance, there is the ability to use the multiple heads on a hard drive or write to multiple sectors with a solid state drive while utilizing multicasting to drive the data. Current technology requires one to manually copy and write multiple times across the system, which interferes with the current running workloads on the system.

At C, there is presented a policy that allows for deciding how the workloads are generated across the system. The policy includes maximum values for the environment and the ability to work independent of location between the lab, datacenter, private cloud, public cloud, etc. A differentiator, with the approaches herein, is that work occurs across the entire landscape of a company or enterprise environment (physical, private clouds, public clouds, etc.).

At D, an identity service authorizes the actions of the techniques to provide access control for every workload being generated. The only workload communicating with the identity service is the first workload. The novelty to this approach is that the workloads are not independent and actually work together as a single unit. Moreover, the ability to separate from a tree organization of workloads is still achievable, if desired, but control for groups of workloads is also achievable.

Internal to the workload is a policy defining how many total workloads to generate and how many can be managed from a single workload. The policy is also able to tell me how many resources can be used between environments. As an example, consider an individual user's cloud that is limited to only three workloads, while a lab environment may have a limit of 100's of clouds. With the approaches herein one can determine where and also apply a priority to the decision. In the single user cloud example, there may be three children on the first level then two children below that level to get the total number of 13 workloads.

At E, Once the new workload in Level 2 is bootstrapped, identity information is obtained, at B and also the updated policy, at C, which now shows where 12 workloads reside now instead of 13 (at B one was created). There is also an option to wait until all the nodes are started before the files are pushed down or the files are immediately copied. There is still another option to have each workload contact the files individually or through the processing at B or Level 1. Once the workload is started then it spawns off the next series of workloads until either a specific total is reached or the directions are dynamically changed. Once the correct actions are finished, a message is sent back to the processing at B, which coordinates the activities.

At F, the same processing is followed as the processing at E: bootstrapping the workload, reading the policy, and completing the identity authorization. Once started, then two more workloads are spawned off following the policy acquisition. At G, is completion processing where there are no more nodes to spawn and so processing returns to B for purposes of completing the call. Notice that my tree is not exactly balanced because the speed of the hardware is leveraged to complete the calls as fast as possible. Furthermore, policy instructions can build the tree in any desired tree pattern, and other types of tree algorithms can be used, or an administrator can process the techniques at any desired optimized rate.

At H, the system is uniquely monitored. Packets are sent along the tree series to have messages delivered securely along the path built. Each node only knows about other nodes connected to it; this provides more security in that no machine has access to every other machine.

At J, the processing allows work to occur independent of the technology so that one can spawn to a public cloud or private cloud. This allows one to integrate and spawn workloads based upon the needs of the organization and independent of the technology being used by that organization. The same bootstrapping happens to the workload with execution of the policy/identity until the request is completed. The policy allows very fine grained control over the spawning along with the interaction that is happening between the workloads.

At I, the processing shows the final return to the workload processor to give confirmation that everything happened or that the current status as properly reported. The techniques herein can also utilize many calls for creating, managing, executing, and deleting the workloads within the enterprise or between enterprises.

FIG. 2 is a diagram of a method 200 for spawning workloads, according to an example embodiment. The method 200 (hereinafter “workload distributor”) is implemented and resides within a non-transitory computer-readable or processor-readable medium that executes on one or more processors of a network. Moreover, the workload distributor is operational over a network and the network may be wired, wireless, or a combination of wired and wireless.

At 210, the workload distributor configures a workload with a deployment policy, an identity-based authentication mechanism, and an access-control mechanism. The deployment policy drives how each instance of the workload is subsequently deployed and initiated in particular processing environments. The deployment policy can include a variety of information as discussed above and below. The identity-based authentication mechanism includes processing for authentication each instance of a workload with an authentication service, such as an identity service for purposes of acquiring a unique identity for each instance. The access-control mechanism includes processing for enforcing role-based and identity-based access to resources within or that access each instance of the workload.

An instance of the workload is a configured copy or duplicate of the workload that may include its own environmental specific configuration. Again, the workload can include such things as a VM, a system, an OS, a service, an application, or various combinations of these types of resources. So, a workload can be a single resource or a composite resource (that includes a variety of cooperating resources).

According to an embodiment, at 211, the workload distributor represents the workload as an imaged copy of the workload. This is what is loaded and installed by an OS and used to initiate an instance of the workload within any particular target processing environment.

In another case, at 212, the workload distributor represents the workload as one or more configuration files that identify resources of the workload, how to acquire, and how to configure and initiate instances of the workload using a multicast or broadcast protocol over a network from the remote repository to the first processing environment.

In yet another situation, at 213, the workload distributor receives a request from a principal (user or automated application). The request identifies a total number of instances for the workload to deploy over a network (can span multiple clouds). The total number of requested instances of the workload is updated to the deployment policy. As each instance of the workload is initiated it receives an updated total number of instances to ensure that the correct number of instances is being deployed over the network.

At 220, the workload distributor deploys a first instance of the workload in a first processing environment. Moreover, the first instance deployed within the first processing environment utilizes the deployment policy, the identity-based authentication mechanism, and the access-control mechanism.

In an embodiment, at 221, the workload distributor multicasts files or an image for the workload over a network to the first processing environment. The files or the image also simultaneously multicast or broadcasts to the additional processing environments (discussed at 240 below). In other words, the configuration information (image or files) is read once from a location accessible to the workload distributor and then multiple instances of the workload (including the first instance) are written and deployed to multiple processing environments. One technique for achieving this is to have the workload distributor multicast the image or files for the workload over a network to the multiple processing environments. Other approaches can be used as well, such as having each deployed instance push the next instance to deployment over the network (as discussed above and again below).

Continuing with the embodiment of 221 and at 222, the workload distributor initiates multiple heads on a hard drive in the first processing environment to write the files or the image on the hard drive of the first processing environment. The workload distributor can also initiate solid state drives or use of multiple buses in the first processing environment to write the files or the image to storage in the first processing environment. In fact, any hardware technology that optimizes storage writes in the first processing environment can be utilized for more efficient write performance. This permits a faster write with more efficient performance that utilizes aspects of the underlying hardware devices, which heretofore has not occurred.

Still continuing with the embodiment of 222 and at 223, the workload distributor starts additional multiple heads on each additional hard drive in the additional processing environments to write the files or the image on the additional hard drives of the additional processing environments. In other words, as each image is written to its processing environment (via the multicast from the source environment of the workload distributor), the write occurs utilizing multiple heads on the hard drives of each target processing environment. This results in efficient and quick deployment of the instances of the workload.

At 230, the workload distributor updates the deployment policy to reflect an occurrence of the first instance. In other words, the deployment policy (or perhaps other metadata associated with the workload) accounts for each instance being deployed, such that as each instance is initiated, each subsequent instance knows how many more instances are needed to fulfill a request for a specific number of instances being deployed on the network.

For example, at 231, the workload distributor decrements a total number of instances for the workload by one within the deployment policy to reflect that the first instance has been deployed already within the first processing environment. So, aspects of the deployment policy (or other metadata carried with each instance) serves as a counter that is decremented as each instance is successfully initiated in its particular target processing environment.

At 240, the workload distributor causes the deployment of additional instances of the workload to additional processing environments using and updating the deployment policy for each additional occurrence of the workload and enforcing the identity-based authentication mechanism and the access-control mechanism. That is, each instance of the workload deployed after the first instance spawns by itself as soon as the first instance is successfully deployed and as each spawned instance is deployed the deployment policy is updated for the next instance that is to spawn and the authentication and access mechanisms are enforced with each deployed instance.

According to an embodiment, at 241, the workload distributor has the first instance from the first processing environment recursively initiate the deployment of a next additional instance based on the updated deployment policy. Each deployed instance pushed deployment of the next instance in a recursive fashion.

Continuing with the embodiment of 241 and at 242, the workload distributor instructs each instance to update the deployment policy to reflect successful deployment of that instance within an image or files that are used for that instance for deployment to a particular additional processing environment. Here, the deployment policy is centrally managed and each instance updates the policy when that instance successfully initiates in its target processing environment.

In an embodiment, at 250, the workload distributor sends messages to each instance within each instances native processing environment for purposes of auditing and monitoring each instance. Monitoring and auditing policies can be enforced centrally via the workload distributor.

FIG. 3 is a diagram of another method 300 for spawning workloads, according to an example embodiment. The method 300 (hereinafter “workload instantiator”) is implemented and resides within a non-transitory computer-readable or processor-readable medium that executes on one or more processors of a network. Moreover, the workload instantiator is operational over a network and the network may be wired, wireless, or a combination of wired and wireless.

The workload instantiator presents another and in some cases enhanced perspective of the workload distributor represented by the method 200 of the FIG. 2 and discussed in detail above. Specifically, the workload instantiator is presented from the perspective of a successfully installed instance of the workload whereas the method 200 is presented from the perspective of an initial deployment site for deployment of a first instance of the workload.

At 310, the workload instantiator initiates an instance of a workload in a first processing environment. In some cases, this can be the first processing environment for a first instance of the workload as discussed above with respect to the method 200 of the FIG. 2. Although, it is noted that the instance can be any instance in a chain of instances for the workload.

According to an embodiment, at 311, the workload instantiator acquires from the instance of the workload from a remote repository that uses a multicast or broadcast protocol or technology mechanism over a network from the remote repository to the first processing environment. In other words, the workload instantiator processes in the first processing environment and receives the workload for creating the instance as an image or files over the network via a multicast or even a broadcast communication from the remote repository.

At 320, the workload instantiator authenticates, via the instance now installed in the first processing environment, with an external identity service (external authentication mechanism, accessible over the network).

In an embodiment, at 321, the workload instantiator indirectly authenticates with the external identity service via communication with a first instance of the workload deployed over a network. In other words, the workload instantiator contacts the first installed network instance of the workload to authenticate with the external identity service, the first installed instance contacts the external identity service on behalf of the instance.

At 330, the workload instantiator enforces, via the instance of the workload, access control defined in the workload. That is, access control for resources accessing the instance or for internal resources of the instance obey access control defined for the workload.

In an embodiment, at 331, the workload instantiator obtains access control policies for the access control from the external identity service. So, access control policies can be dynamic and ever changing since authentication provides the access control policies dynamically to the instance.

At 340, the workload instantiator decrements a total number of instances for the workload defined in a deployment policy by one. When the instance is successfully up and running in the first processing environment, the number of deployed instances for the workload is updated so that each subsequent instance that is deployed knows how many more instances are needed based on the deployment policy.

According to an embodiment, at 341, the workload instantiator modifies the deployment policy as metadata carried with the instance. Here, a next installed instance of the workload uses the metadata that is modified when that particular instance is deployed in its target processing environment.

In another case, at 342, the workload instantiator modifies the deployment policy as metadata associated with the workload and centrally housed in a remote repository over a network. So, a central location manages the deployment policy; rather than the decentralized approach discussed at 341.

At 350, the workload instantiator deploys a next instance of the workload when the total number of deployed instances is non zero (greater than zero) to a next processing environment. Deployment occurs from the first processing environment to the next processing environment. So, each deployed instance causes or pushes the next deployed instance.

It is noted that a single processing environment can have multiple deployed instances.

FIG. 4 is a diagram of a workload spawning system 400, according to the techniques presented herein. The components of the workload spawning system 400 are implemented within and reside within a non-transitory and computer or processor-readable storage medium for purposes of executing on one or more processors of a network. The network may be wired, wireless, or a combination of wired and wireless.

The workload spawning system 400 implements, inter alia, various aspects of the FIG. 1, and the method 200 and the method 300 of the FIGS. 2 and 3, respectively.

The workload spawning system 400 includes a deployment manager 401 and an instance of a workload 402. Each of these components and their interactions with one another will now be discussed in detail.

The deployment manager 401 is implemented in a non-transitory computer-readable storage medium for execution on one or more processors of a network. Example aspects of the deployment manager 401 were discussed above with respect to the FIGS. 1 and 2.

The deployment manager 401 is configured to deploy at least the instance of the workload 402 to a target processing environment.

According to an embodiment, the deployment manager 401 is configured to include authentication and access control services in configuration data associated with the workload.

The instance of the workload 402 is implemented in a non-transitory computer-readable storage medium for execution on one or more of the processors of a network. Example aspects of the instance of the workload 402 were presented above with respect to the FIGS. 1 and 3.

The instance of the workload 402 includes a deployment policy that identifies a total number of instances of the workload for deployment over the network. The instance of the workload 402 configured to cause additional deployments of remaining instances of the workload over the network to additional target processing environments using an updated deployment policy.

According to an embodiment, each of the remaining instances decrement the total number of instances once operable in a particular additional target processing environment within the deployment policy.

The above description is illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of embodiments should therefore be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. 

1. (canceled)
 2. A method, comprising: deploying a parent workload to a first environment using a deployment policy; and initiating, by the parent workload, one or more child instances of the parent workload to one or more second environments, the parent workload and the child instances cooperate to act as a single unit and the single unit managed by the parent workload.
 3. The method of claim 2, wherein deploying further includes defining the parent workload through a configuration file.
 4. The method of claim 2, wherein deploying further includes deploying the parent workload as a processing image to the first environment.
 5. The method of claim 2, wherein deploying further includes configuring the parent workload with a total number of permissible child instances for the parent workload to manage.
 6. The method of claim 5, wherein configuring further includes receiving the total number from a principal.
 7. The method of claim 5, wherein configuring further includes defining the total number via a policy internal to the parent workload and enforced by the parent workload.
 8. The method of claim 2, wherein initiating further includes multicasting the one or more instances simultaneously over a network to the one or more second environments.
 9. The method of claim 2, wherein initiating further includes spawning, by the parent workload, each of the one or more instances to the one or more second environments until a total number or pre-defined instances is reached.
 10. The method of claim 2, wherein initiating further includes, spawning, by the parent workload, at least one instance to a public cloud processing environment and at least one additional instance to a private cloud processing environment.
 11. A method, comprising: authenticating, by a first instance of a workload, to an identity service from a first processing environment; spawning, by the first instance, a number of additional instances of the workload, each additional instance spawned to a different processing environment; and managing, by the first instance, the additional instances from the first processing environment.
 12. The method of claim 11 further comprising, coordinating, by the first instance, cooperating of the additional instances among one another to act as a single processing instance.
 13. The method of claim 11, wherein authenticating further includes obtaining, by the first instance, access policies to enforce against each of the additional instances upon successful authentication to the identity service.
 14. The method of claim 11, wherein spawning further includes enforcing, by the first instance, a deployment policy while spawning the additional instances.
 15. The method of claim 12, wherein enforcing further includes obtaining from the deployment policy a total number of the additional instance to deploy and identifiers for each additional instance's processing environment.
 16. The method of claim 11, wherein managing further includes controlling, by the first instance, resources accessible to each of the additional instances.
 17. The method of claim 11, wherein managing further includes organizing, by the first instance, the additional instances as a managed tree.
 18. The method of claim 11, wherein managing further includes prioritizing, by the first instance, distributed actions for processing by the additional instances based on enforcement of a policy.
 19. A system, comprising: a processor; and a first instance of a workload adapted and configured to: i) execute on the process associated with a device in a first processing environment, ii) deploy two or more additional instances of the workload over a network to two or more different processing environments, and iii) coordinate the two or more additional instances to act as a collective unit for processing actions over the network.
 20. The system of claim 19, wherein the first instance is further adapted and configured, in ii), to: multicast the deployment of the two or more additional instances over the network.
 21. The system of claim 19, wherein the first instance is further adapted and configured, in iii), to: act as an intermediary between the two or more additional instances and an identity service for authentication and access control enforcement associated with the two or more additional instances. 